Skip to content

build(vm): re-pin both rootfs images for Go 1.26.10 - #302

Merged
Ash20pk merged 2 commits into
mainfrom
build/vm-repin-go-1.26.10
Oct 25, 2026
Merged

Ash20pk merged 2 commits into
mainfrom
build/vm-repin-go-1.26.10

Conversation

@Ash20pk

@Ash20pk Ash20pk commented Oct 25, 2026

Copy link
Copy Markdown
Owner

The publish from main (run 40216091795) stopped before publishing anything. Alpine moved go to 1.26.10 and libcurl to 8.23.0 a few hours after the last re-pin, so semantic-fs-daemon no longer built to its pin on either architecture.

  • New semantic-fs-daemon and rootfs pins, from update_pins runs 40217496771 (aarch64) and 40217494503 (x86_64): rootfs dfb5f6b0… and af4f3fc0…. Sizes and kernels are unchanged.
  • New berth-vmm pins for all three platforms from run 40219221120, which also rebuilt both rootfs images to their pins and passed the x86_64 e2e. libkrun is unchanged.
  • Release names in the CLI and docs move to vm-artifacts-8f79e8da-dfb5f6b0 and vm-artifacts-10d4b54c-af4f3fc0.

This is open problem 10 again. Publish straight after merging so the pins don't drift a third time.

The publish from main (run 40216091795) stopped at the guest build:
Alpine moved go to 1.26.10 and libcurl to 8.23.0, so semantic-fs-daemon
no longer built to its pin. New pins from update_pins runs 40217496771
(aarch64) and 40217494503 (x86_64).
Run 40219221120 built all three, rebuilt both rootfs images to their
pins, and passed the x86_64 e2e. libkrun is unchanged.
@Ash20pk
Ash20pk merged commit ca3605c into main Oct 25, 2026
36 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant